Hosted Cloud MX Records
Mail Exchange (MX) records are DNS records that are necessary for delivering email to your address.
An MX record is used to tell the world which mail servers accept incoming mail for your domain and where emails sent to your domain should be routed. Assigning multiple MX records is a fail-safe measure you can use in the event your default mail server is down. If your MX records do not point to the correct location you will not receive email.
To route incoming email for your domain through the Spam Experts filter you need to update the MX records in your domain provider's DNS settings.
The default MX records are listed in the Default MX host names section in the General > Settings page accessible from the Admin Level Control Panel,
You can check whether your domains have the correct MX Records configured using the
Update Your MX Records in Your Domain Provider's DNS Settings
- In your domain provider's DNS control panel add the appropriate MX records:
- Remove the original MX records
- Check, using the Log Search, that the message has passed through the Spam Experts filtering nodes
- mx.spamexperts.com (priority 10)
- fallbackmx.spamexperts.eu (priority 20)
- lastmx.spamexperts.net (priority 30)
- filter10.antispamcloud.com (priority 10)
- filter20.antispamcloud.com (priority 20)
- filter30.antispamcloud.com (priority 30)
- filter40.antispamcloud.com (priority 40)
MX records consist of two parts: the domain name and the priority: the lowest number is the highest priority and is the first one attempted for delivery. Be sure to include the priority when adding the MX records
You must make sure you remove old MX records so that all emails are filtered through the Spam Experts cloud. Spammers actively try different MX records (such as the highest numbered priority) to bypass spam filters.
DNS changes can take some time to propagate to DNS resolvers world-wide, meaning email may continue to deliver directly to the previous MX records without filtering for some time, depending on the TTL value for the MX records
Global MX Records (Recommended)
For redundancy reasons we recommend using our global records. Our up-time and service level guarantees do not apply to the EU/US-only records:
Region-Specific MX Records
However, where there is a requirement to route data through a specific geographic territory, the below region-specific MX records may be used:
| Region | Priority | TTL (recommended) | Region | Priority | TTL (recommended) | |
|---|---|---|---|---|---|---|
| European Union (EU) | United States (US) | |||||
| mx1-eu.spamexperts.com | 10 | 300 | mx1-us.spamexperts.com | 10 | 300 | |
| mx2-eu.spamexperts.com | 20 | 300 | mx2-us.spamexperts.com | 20 | 300 | |
| mx3-eu.spamexperts.com | 30 | 300 | mx3-us.spamexperts.com | 30 | 300 | |
| mx4-eu.spamexperts.com | 40 | 300 | mx4-us.spamexperts.com | 40 | 300 | |
| United Kingdom (UK) | Australia (AU) | |||||
| mx1-uk.spamexperts.com | 10 | 300 | mx1-au.spamexperts.com | 10 | 300 | |
| mx2-uk.spamexperts.com | 20 | 300 | mx2-au.spamexperts.com | 20 | 300 | |
| mx3-uk.spamexperts.com | 30 | 300 | mx3-au.spamexperts.com | 30 | 300 | |
| mx4-uk.spamexperts.com | 40 | 300 | mx4-au.spamexperts.com | 40 | 300 | |
| Canada (CA) Region | South Africa (ZA) Region | |||||
| mx1-ca.spamexperts.com | 10 | 300 | mx1-za.spamexperts.com | 10 | 300 | |
| mx2-ca.spamexperts.com | 20 | 300 | mx2-za.spamexperts.com | 20 | 300 | |
| mx3-ca.spamexperts.com | 30 | 300 | mx3-za.spamexperts.com | 30 | 300 | |
| mx4-ca.spamexperts.com | 40 | 300 | mx4-za.spamexperts.com | 40 | 300 |
Private Label MX Records
Global Private Label MX Records
Usage of these records without a private label license leads to filtering automatically being suspended.
For redundancy reasons we recommend using our global records. Our up-time and service level guarantees do not apply to the EU/US-only records.
GDPR does NOT require email to be routed only via a specific geographical region.
Region-Specific Private Label MX Records
However, where there is a requirement to route data through a specific geographic territory, the below region-specific MX records may be used:
| Region | Priority | TTL (recommended) | Region | Priority | TTL (recommended) | |
|---|---|---|---|---|---|---|
| European Union (EU) | United States (US) | |||||
| filter10-eu.antispamcloud.com. | 10 | 300 | filter10-us.antispamcloud.com. | 10 | 300 | |
| filter20-eu.antispamcloud.com. | 20 | 300 | filter20-us.antispamcloud.com. | 20 | 300 | |
| filter30-eu.antispamcloud.com. | 30 | 300 | filter30-us.antispamcloud.com. | 30 | 300 | |
| filter40-eu.antispamcloud.com. | 40 | 300 | filter40-us.antispamcloud.com. | 40 | 300 | |
| United Kingdom (UK) | Australia (AU) | |||||
| filter10-uk.antispamcloud.com. | 10 | 300 | filter10-au.antispamcloud.com. | 10 | 300 | |
| filter20-uk.antispamcloud.com. | 20 | 300 | filter20-au.antispamcloud.com. | 20 | 300 | |
| filter30-uk.antispamcloud.com. | 30 | 300 | filter30-au.antispamcloud.com. | 30 | 300 | |
| filter40-uk.antispamcloud.com. | 40 | 300 | filter40-au.antispamcloud.com. | 40 | 300 | |
| Canada (CA) Region | South Africa (ZA) Region | |||||
| filter10-ca.antispamcloud.com. | 10 | 300 | filter10-za.antispamcloud.com | 10 | 300 | |
| filter20-ca.antispamcloud.com. | 20 | 300 | filter20-za.antispamcloud.com | 20 | 300 | |
| filter30-ca.antispamcloud.com. | 30 | 300 | filter30-za.antispamcloud.com | 30 | 300 | |
| filter40-ca.antispamcloud.com. | 40 | 300 | filter40-za.antispamcloud.com | 40 | 300 |
Some DNS control panels require you to use a trailing dot (.) after the hostname. Please check with your DNS provider if this is the case for you.
Custom MX Records
Before adding the MX records to your domain, please open a support ticket so that your hostnames will get added to the spamrl.com nameservers, as they will only function once we create them at our end.
Custom MX records are not available for trial users on our Hosted Cloud.
To create your own MX-record hostnames, you need to setup 4 NS-record hostnames in your DNS pointing to our nameservers:
mx1.demo-domain.invalid. NS dns1.spamrl.com.
mx1.demo-domain.invalid. NS dns2.spamrl.com.
mx1.demo-domain.invalid. NS dns3.spamrl.com.
mx1.demo-domain.invalid. NS dns4.spamrl.com.
mx2.demo-domain.invalid. NS dns1.spamrl.com.
mx2.demo-domain.invalid. NS dns2.spamrl.com.
mx2.demo-domain.invalid. NS dns3.spamrl.com.
mx2.demo-domain.invalid. NS dns4.spamrl.com.
mx3.demo-domain.invalid. NS dns1.spamrl.com.
mx3.demo-domain.invalid. NS dns2.spamrl.com.
mx3.demo-domain.invalid. NS dns3.spamrl.com.
mx3.demo-domain.invalid. NS dns4.spamrl.com.
mx4.demo-domain.invalid. NS dns1.spamrl.com.
mx4.demo-domain.invalid. NS dns2.spamrl.com.
mx4.demo-domain.invalid. NS dns3.spamrl.com.
mx4.demo-domain.invalid. NS dns4.spamrl.com.
The domain that you want to apply filtering to then can use your personal MX records as follows:
yourdomain.ext. MX 10 mx1.demo-domain.invalid.
yourdomain.ext. MX 20 mx2.demo-domain.invalid.
yourdomain.ext. MX 30 mx3.demo-domain.invalid.
yourdomain.ext. MX 40 mx4.demo-domain.invalid.
Some DNS control panels do not require you to use a trailing dot (.) after the hostname. Please check with your DNS provider if this is the case for you.
As CNAME hostnames are not supported for MX record hostnames, you can alternatively use an ALIAS DNS record pointing to your custom MX-record hostname in case you need more than 1 set of MX-record hostnames.
For information on Local Cloud MX records, please see the Local Cloud MX Records page in the full documentation.